Skip to content

Weekly cargo update #139727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 21, 2025
Merged

Weekly cargo update #139727

merged 1 commit into from
Apr 21, 2025

Conversation

github-actions[bot]
Copy link

Automation to keep dependencies in Cargo.lock current.

The following is the output from cargo update:

compiler & tools dependencies:
     Locking 11 packages to latest compatible versions
    Updating bstr v1.11.3 -> v1.12.0
    Updating clap v4.5.35 -> v4.5.36
    Updating clap_builder v4.5.35 -> v4.5.36
    Updating crossbeam-channel v0.5.14 -> v0.5.15
    Updating jiff v0.2.5 -> v0.2.6
    Updating jiff-static v0.2.5 -> v0.2.6
    Updating jsonpath-rust v1.0.0 -> v1.0.1
    Updating linux-raw-sys v0.9.3 -> v0.9.4
    Updating miniz_oxide v0.8.7 -> v0.8.8
    Updating self_cell v1.1.0 -> v1.2.0
    Updating winnow v0.7.4 -> v0.7.6
note: pass `--verbose` to see 38 unchanged dependencies behind latest

library dependencies:
     Locking 1 package to latest compatible version
    Updating miniz_oxide v0.8.7 -> v0.8.8
note: pass `--verbose` to see 4 unchanged dependencies behind latest

rustbook dependencies:
     Locking 9 packages to latest compatible versions
    Updating bstr v1.11.3 -> v1.12.0
    Updating cc v1.2.18 -> v1.2.19
    Updating clap v4.5.35 -> v4.5.36
    Updating clap_builder v4.5.35 -> v4.5.36
    Updating jiff v0.2.5 -> v0.2.6
    Updating jiff-static v0.2.5 -> v0.2.6
    Updating linux-raw-sys v0.9.3 -> v0.9.4
    Updating miniz_oxide v0.8.7 -> v0.8.8
    Updating winnow v0.7.4 -> v0.7.6

compiler & tools dependencies:
     Locking 11 packages to latest compatible versions
    Updating bstr v1.11.3 -> v1.12.0
    Updating clap v4.5.35 -> v4.5.36
    Updating clap_builder v4.5.35 -> v4.5.36
    Updating crossbeam-channel v0.5.14 -> v0.5.15
    Updating jiff v0.2.5 -> v0.2.6
    Updating jiff-static v0.2.5 -> v0.2.6
    Updating jsonpath-rust v1.0.0 -> v1.0.1
    Updating linux-raw-sys v0.9.3 -> v0.9.4
    Updating miniz_oxide v0.8.7 -> v0.8.8
    Updating self_cell v1.1.0 -> v1.2.0
    Updating winnow v0.7.4 -> v0.7.6
note: pass `--verbose` to see 38 unchanged dependencies behind latest

library dependencies:
     Locking 1 package to latest compatible version
    Updating miniz_oxide v0.8.7 -> v0.8.8
note: pass `--verbose` to see 4 unchanged dependencies behind latest

rustbook dependencies:
     Locking 9 packages to latest compatible versions
    Updating bstr v1.11.3 -> v1.12.0
    Updating cc v1.2.18 -> v1.2.19
    Updating clap v4.5.35 -> v4.5.36
    Updating clap_builder v4.5.35 -> v4.5.36
    Updating jiff v0.2.5 -> v0.2.6
    Updating jiff-static v0.2.5 -> v0.2.6
    Updating linux-raw-sys v0.9.3 -> v0.9.4
    Updating miniz_oxide v0.8.7 -> v0.8.8
    Updating winnow v0.7.4 -> v0.7.6
@rustbot
Copy link
Collaborator

rustbot commented Apr 13, 2025

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 13, 2025
@rustbot
Copy link
Collaborator

rustbot commented Apr 13, 2025

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

These commits modify the library/Cargo.lock file. Unintentional changes to library/Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

@clubby789 clubby789 closed this Apr 13, 2025
@clubby789 clubby789 reopened this Apr 13, 2025
@Mark-Simulacrum
Copy link
Member

@bors r+ rollup=iffy

@bors
Copy link
Collaborator

bors commented Apr 19, 2025

📌 Commit 330daad has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 19, 2025
bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 20, 2025
…acrum

Weekly `cargo update`

Automation to keep dependencies in `Cargo.lock` current.

The following is the output from `cargo update`:

```txt

compiler & tools dependencies:
     Locking 11 packages to latest compatible versions
    Updating bstr v1.11.3 -> v1.12.0
    Updating clap v4.5.35 -> v4.5.36
    Updating clap_builder v4.5.35 -> v4.5.36
    Updating crossbeam-channel v0.5.14 -> v0.5.15
    Updating jiff v0.2.5 -> v0.2.6
    Updating jiff-static v0.2.5 -> v0.2.6
    Updating jsonpath-rust v1.0.0 -> v1.0.1
    Updating linux-raw-sys v0.9.3 -> v0.9.4
    Updating miniz_oxide v0.8.7 -> v0.8.8
    Updating self_cell v1.1.0 -> v1.2.0
    Updating winnow v0.7.4 -> v0.7.6
note: pass `--verbose` to see 38 unchanged dependencies behind latest

library dependencies:
     Locking 1 package to latest compatible version
    Updating miniz_oxide v0.8.7 -> v0.8.8
note: pass `--verbose` to see 4 unchanged dependencies behind latest

rustbook dependencies:
     Locking 9 packages to latest compatible versions
    Updating bstr v1.11.3 -> v1.12.0
    Updating cc v1.2.18 -> v1.2.19
    Updating clap v4.5.35 -> v4.5.36
    Updating clap_builder v4.5.35 -> v4.5.36
    Updating jiff v0.2.5 -> v0.2.6
    Updating jiff-static v0.2.5 -> v0.2.6
    Updating linux-raw-sys v0.9.3 -> v0.9.4
    Updating miniz_oxide v0.8.7 -> v0.8.8
    Updating winnow v0.7.4 -> v0.7.6
```
@bors
Copy link
Collaborator

bors commented Apr 20, 2025

⌛ Testing commit 330daad with merge ff33eee...

@rust-log-analyzer
Copy link
Collaborator

The job x86_64-apple-1 failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
failures:

---- [mir-opt] tests/mir-opt/strip_debuginfo.rs#NONE stdout ----

thread '[mir-opt] tests/mir-opt/strip_debuginfo.rs#NONE' panicked at src/tools/compiletest/src/runtest.rs:1516:17:
failed to remove and recreate output directory `/Users/runner/work/rust/rust/build/x86_64-apple-darwin/test/mir-opt/strip_debuginfo`: Directory not empty (os error 66)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    [mir-opt] tests/mir-opt/strip_debuginfo.rs#NONE

@bors
Copy link
Collaborator

bors commented Apr 20, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Apr 20, 2025
@clubby789
Copy link
Contributor

failed to remove and recreate output directory `/Users/runner/work/rust/rust/build/x86_64-apple-darwin/test/mir-opt/strip_debuginfo`: Directory not empty (os error 66)

Seems spurious, and no bumped deps seem relevant
@bors retry

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 20, 2025
@bors
Copy link
Collaborator

bors commented Apr 21, 2025

⌛ Testing commit 330daad with merge c8f9423...

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 21, 2025
… r=<try>

[EXPERIMENTAL] `tests/mir-opt/strip_debuginfo.rs` failure investigation

cc rust-lang#140096 (comment), rust-lang#139727 (comment).

r? ghost

try-job: x86_64-apple-1
try-job: x86_64-msvc-1
try-job: dist-x86_64-msvc
@jieyouxu
Copy link
Member

Backlink: #134351

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 21, 2025
… r=<try>

[EXPERIMENTAL] `tests/mir-opt/strip_debuginfo.rs` failure investigation

cc rust-lang#140096 (comment), rust-lang#139727 (comment).
cf. rust-lang#134351.

(Yes this isn't robust, but just in case)

r? ghost

try-job: x86_64-apple-1
try-job: x86_64-msvc-1
try-job: dist-x86_64-msvc
@bors
Copy link
Collaborator

bors commented Apr 21, 2025

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing c8f9423 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Apr 21, 2025
@bors bors merged commit c8f9423 into master Apr 21, 2025
7 checks passed
@bors bors deleted the cargo_update branch April 21, 2025 15:15
@rustbot rustbot added this to the 1.88.0 milestone Apr 21, 2025
Copy link
Author

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing b8005bf (parent) -> c8f9423 (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard c8f94230282a8e8c1148f3e657f0199aad909228 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. x86_64-apple-1: 5922.1s -> 8568.2s (44.7%)
  2. dist-aarch64-linux: 7924.8s -> 5499.9s (-30.6%)
  3. dist-apple-various: 6583.1s -> 7990.7s (21.4%)
  4. dist-x86_64-apple: 8767.9s -> 10601.1s (20.9%)
  5. dist-aarch64-apple: 4506.2s -> 4946.0s (9.8%)
  6. dist-powerpc-linux: 5021.2s -> 5361.8s (6.8%)
  7. dist-loongarch64-linux: 6347.1s -> 6725.3s (6.0%)
  8. x86_64-msvc-1: 8556.6s -> 9040.3s (5.7%)
  9. dist-x86_64-mingw: 7502.4s -> 7922.0s (5.6%)
  10. x86_64-msvc-2: 6790.0s -> 7150.5s (5.3%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (c8f9423): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (primary -0.6%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
1.4% [0.6%, 2.1%] 2
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.4% [-3.0%, -0.5%] 5
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.6% [-3.0%, 2.1%] 7

Cycles

Results (primary 0.5%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
0.5% [0.4%, 0.6%] 2
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.5% [0.4%, 0.6%] 2

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 773.608s -> 774.633s (0.13%)
Artifact size: 365.05 MiB -> 365.03 MiB (-0.01%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants